Skip to content

Treat explicit imports from node_modules as external library imports#16364

Merged
4 commits merged into
masterfrom
explicit-node_modules
Aug 17, 2017
Merged

Treat explicit imports from node_modules as external library imports#16364
4 commits merged into
masterfrom
explicit-node_modules

Conversation

@ghost

@ghost ghost commented Jun 8, 2017

Copy link
Copy Markdown

Fixes #15970 and #15755

Comment thread src/compiler/types.ts
export interface ResolvedModule {
/** Path of the file the module was resolved to. */
resolvedFileName: string;
/**

@ghost ghost Jun 8, 2017

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This comment didn't describe what we're actually doing. We don't validate the contents of files in any way while doing module resolution.

@ghost ghost requested a review from aozgaa July 10, 2017 19:50
@aozgaa

aozgaa commented Aug 15, 2017

Copy link
Copy Markdown
Contributor

I'm not sure what the ramifications of turning everything in node_modules into external library imports is (aside from avoiding the inadvertent compilation of *.js files in the linked issues).

Specifically, what changes in our treatment of a module when it is an external library import vs. an import within the project?

@aozgaa

aozgaa commented Aug 17, 2017

Copy link
Copy Markdown
Contributor

Talked offline, LGTM

@ghost ghost merged commit eef7d8b into master Aug 17, 2017
@ghost ghost deleted the explicit-node_modules branch August 17, 2017 20:26
@microsoft microsoft locked and limited conversation to collaborators Jun 14, 2018
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants